Communication apparatus, system, method, allocation apparatus, and non-transitory recording medium

ABSTRACT

Traffic is allocated to a dedicated apparatus that performs a predetermined network function or a predetermined virtual network function corresponding to the predetermined network function of the dedicated apparatus, according to a service level set in correspondence with information relating to the traffic, and the traffic is forwarded to the dedicated apparatus or the predetermined virtual network function, based on a result of the allocation.

REFERENCE TO RELATED APPLICATION

The present application is a continuation application of U.S. patentapplication Ser. No. 16/836,234 filed on Mar. 31, 2020, which is issuedas U.S. Pat. No. 11,317,316, which is a continuation application of U.S.patent application Ser. No. 15/557,650 filed on Sep. 12, 2017, which isissued as U.S. Pat. No. 10,638,354, which is a National Stage Entry ofinternational application PCT/JP2016/057522, filed on Mar. 10, 2016,which claims the benefit of priority from Japanese Patent Application2015-051225 filed on Mar. 13, 2015, the disclosures of all of which areincorporated in their entirety by reference herein.

TECHNICAL FIELD

The present invention relates to a communication apparatus, a system, amethod, an allocation apparatus, and a non-transitory recording medium.In particular, it relates to an apparatus, a system, a method, and aprogram suitably applied to mobile networks.

BACKGROUND

MVNO (Mobile Virtual Network Operator), which is a business form thatprovides mobile communication services, does not have its own radiocommunication infrastructures or the like, but leases necessaryinfrastructure such as radio communication infrastructure from MNO(Mobile Network Operator) and do mobile communication businesses underits own brand.

<L3 Connection>

In the case of an MVNO in Layer 3 (L3: network layer) connection, asschematically illustrated in FIG. 19A, a GTP (GPRS (General Packet RadioService) Tunneling Protocol) session (Layer 2: L2) for forwarding an IP(Internet Protocol) packet from an end user is terminated within anetwork (core network) of an MNO. The MVNO in L3 connection only needsto prepare in an MVNO network 3 a router or the like that provides L3communication services.

FIG. 19B schematically illustrates an example of a mode of the MVNO inL3 connection. FIG. 19B schematically illustrates a configurationexample in which an EPC (Evolved Packet Core) accommodating an existing2G/3G network and an LTE (Long Term Evolution) access network defined by3GPP (3rd Generation Partnership Project) is configured as an MNOnetwork 2 and the MVNO network 3 including a router such as an edgerouter and a server (not illustrated) is connected to the Internet 4.Here, individual nodes in EPC will be briefly described (reference maybe made to for example, 3GPP TS 23.401 V9.5.0 (2010-06) for details ofthese nodes).

An MME (Mobility Management Entity) performs various kinds of processingsuch as mobility management and authentication of a terminal (mobileterminal) 1 (User Equipment: UE) and setting of a user data forwardingpath. In addition, the MME performs user authentication or the like incooperation with HSS (Home Subscriber Server) (retaining a subscriberprofile). Furthermore, the MME is connected to an SGSN (Serving GPRSSupport Node) that is connected to a (3rd Generation:3G) controlstation/base station (RNC (Radio Network Controller)/NodeB)) andperforms position registration and so forth of a 3G terminal. MME setsand releases a user data forwarding path in an interval (S1-U) betweenan SGW (Serving Gateway) and a base station eNB (eNodeB).

An SGW exchanges user data with an eNB and sets and releases acommunication path with a PGW (PDN (Packet Data Network) Gateway). ThePGW is connected to a packet data network (PDN) such as an IMS (IPMultimedia Subsystem), the Internet, etc. and performs, for example,allocation of an IP (Internet Protocol) address (private IP address) toa terminal. A PCRF (Policy and Charging Rules Function) is a policycontrol apparatus that performs policy control based on a QoS (Qualityof Service) or the like and determines a charging control rule(s). A PGWand an SGW perform policy control, for example, on a per packet basis,based on notification information (policies) from the PCRF. In FIG. 19B,a reference symbol such as S11, etc., given to a line between nodesrepresents an interface. In addition, a dashed line and a solid linerepresent a signal (data) of a control plane (C-Plane) and of a userplane (U-Plane), respectively.

In the case of L3 connection, MVNO does not directly perform operationof a PGW (or GGSN (Gateway GPRS Support Node) (not illustrated)), whichis a packet relay apparatus on the MVO network 2. Allocation of an IPaddress to the terminal (mobile terminal) 1 is performed by a PGW of theMNO, for example. In L3 connection, communication control at the MVNO isperformed in L3 (network layer). In addition, a packet forwardingamount, which is information necessary for charging and the like, isgenerally a daily or monthly forwarding amount provided by the MNO.

<L2 Connection>

In the case of an MVNO in Layer 2 (L2: data link layer) connection, asschematically illustrated in FIG. 20A, a GTP session from an end user isextended to the MVNO. The MVNO needs to arrange a packet relay apparatusin the MVNO network. A GTP tunnel in L2 is terminated at a PGW (or GGSN)provided in the MVNO network, for example.

FIG. 20B schematically illustrates an example of a mode of the MVNO inL2 connection. FIG. 20B schematically illustrates a configurationexample in which an EPC is used as the MNO network 2 and the MVNOnetwork 3 including an PGW is connected to the Internet 4.

The L2 connection is a connection mode in which the terminal 1 used byan end user is connected to the PGW of the MVNO via an L2 tunnel (GTP).Since the MVNO has the PGW, the MVNO can perform various kinds ofcontrol processing. In addition, various kinds of control servers may bearranged adjacent to the PGW on the MVNO network 3. Examples of theseservers may include a RADIUS server (not illustrated) that performs, forexample, management and authentication of users, an OCS (Online ChargingSystem) (not illustrated) that manages data capacity and charginginformation about users, a PCRF (Policy and Charging Rules Function)that manages communication rules for each user, a PCEF (Policy andEnforcement Function) (not illustrated) that applies rules to the PGWand controls packet forwarding, and so forth. A packet relay apparatussuch as the PGW and servers are technically more advanced and moreexpensive than an IP router, etc. Thus, in the MVNO of L2 connection, acost required for operation, maintenance and so forth of the PGW, etc.becomes higher as compared with the L3 connection mode in which the MVNOonly needs to prepare a router. However, the MVNO in L2 connection canperform band width control, etc. by using the PGW, etc. on the MVNOnetwork 3.

CITATION LIST Non-Patent Literature

-   NPL 1: ETSI GS NFV-MAN 001 V1.1.1 (2014-12) Network Functions    Virtualisation (NFV); Management and Orchestration, searched on Jan.    25, 2015,-   Internet<http://www.etsi.org/deliver/etsi_gs/NFV-MAN/001_099/001/0    1.01.01_60/gs_NFV-MAN001v010101p.pdf>

SUMMARY

The following describes an analysis made by the present inventors.

As described above, an MVNO does not construct its own radiocommunication facilities, etc. Instead, the MVNO, by leasing radiocommunication facilities, etc., from a MNO which is a lending sourcethereof, provides a user with services at a low price. Thus, as seenfrom comparison between services provided by an MVNO and an MNO, it isoften the case that the MVNO provides limited services. For example,

a communication speed is slow;

a maximum use capacity per month is low; and

provided no added function, such as voice communication, etc.

For example, when an MVNO is going to impose a limit on a user trafficor the like, under the present circumstances, a certain node such as agateway in an MVNO network performs a traffic shaping (bandwidthcontrol) or the like. For example, the traffic shaping is performed onan S1-U interface between an eNB and an SGW in an EPC, which is the MVNOnetwork.

In principle, the MVNO uses resources and services (for example,bandwidth) provided by the MNO and pays for the resources and servicesthat the MVNO has used. For example, in the case of the MVNO of L3connection, generally, charging is determined by the connectionbandwidth between the MVNO and the MNO (for example, the band width at areference point SGi in FIG. 19B). The MVNO provides a service (forexample, bandwidth) according to an amount (payment amount etc. of acustomer) to the customer.

Thus, it is desirable that the service (for example, bandwidth) providedto a customer can be flexibly controlled.

However, a bandwidth control is generally performed based on a predictedtraffic amount or the like. Thus, a flexible and accurate bandwidthcontrol is difficult. For example, depending on the traffic amount,there is a possibility that a considerable amount of error would occurbetween a predicted value and an actual value.

In particular, an MVNO of L3 connection that does not have a packetforwarding apparatus such as a PGW cannot perform a real-time bandwidthcontrol. Thus, there may be a case wherein a user traffic, which doesnot particularly need a high-function and high-performance apparatus, isallocated to a high-performance and high-performance apparatus.Conversely, there is another case wherein a user traffic, which needs ahigh-function and high-performance apparatus is allocated to alow-function and low-performance apparatus. Both of the above cases arefar from effective use of resources and services.

Thus, the present invention has been made in view of the above problems,and it is an object of the present invention to provide an apparatus, asystem, a method, and a non-transitory recording medium storing aprogram, each of which can realize appropriate allocation of resourcesfor processing traffic to improve resource utilization efficiency.

According to an aspect of the present invention, there is provided anapparatus including: a first unit operable so as to allocate traffic toa dedicated apparatus that performs a predetermined network function ora predetermined virtual network function corresponding to thepredetermined network function of the dedicated apparatus, according toa service level set in correspondence with information relating to thetraffic; and

a second unit operable so as to forward the traffic to the dedicatedapparatus or the predetermined virtual network function based on aresult of the allocation.

According to another aspect of the present invention, there is provideda method comprising:

allocating traffic to a dedicated apparatus that performs apredetermined network function or a predetermined virtual networkfunction corresponding to the predetermined network function of thededicated apparatus, according to a service level set in correspondencewith information relating to the traffic; and

forwarding the traffic to the dedicated apparatus or the predeterminedvirtual network function based on a result of the allocation.

According to still another aspect of the present invention, there isprovided a non-transitory computer-readable recording medium storingtherein a program causing a computer to perform processing comprising:

allocating traffic to a dedicated apparatus that performs apredetermined network function or a predetermined virtual networkfunction corresponding to the predetermined network function of thededicated apparatus, according to a service level set in correspondencewith information relating to the traffic; and

forwarding the traffic to the dedicated apparatus or the predeterminedvirtual network function based on a result of the allocation. Thenon-transitory computer-readable recording medium is such as a computerreadable storage device in which the program is recorded.

According to still another aspect of the present invention, there isprovided a server apparatus, including a plurality of virtual networkfunctions with different processing performances, on a plurality ofvirtual machines, wherein the server apparatus selects, according to aservice level relating to received traffic, one out of the plurality ofvirtual network functions to allocate the traffic to the selectedvirtual network function.

According to the present invention, resources for processing traffic canappropriately be allocated, and resource utilization efficiency can beimproved. Still other features and advantages of the present inventionwill become readily apparent to those skilled in this art from thefollowing detailed description in conjunction with the accompanyingdrawings wherein only exemplary embodiments of the invention are shownand described, simply by way of illustration of the best modecontemplated of carrying out this invention. As will be realized, theinvention is capable of other and different embodiments, and its severaldetails are capable of modifications in various obvious respects, allwithout departing from the invention. Accordingly, the drawing anddescription are to be regarded as illustrative in nature, and not asrestrictive.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A and FIG. 1B are diagrams illustrating an example of a basicconcept of the present invention.

FIG. 2A and FIG. 2B are diagrams illustrating an example of anallocation apparatus in FIG. 1 .

FIG. 3 is a diagram illustrating example embodiment 1 of the presentinvention.

FIG. 4 is a diagram illustrating an example of example embodiment 1 ofthe present invention.

FIG. 5A and FIG. 5B are diagrams illustrating example embodiment 1-1 ofthe present invention.

FIG. 6 is a diagram illustrating a variation of example embodiment 1-1of the present invention.

FIG. 7A and FIG. 7B are diagrams illustrating example embodiment 1-2 ofthe present invention.

FIG. 8A and FIG. 8B are diagrams illustrating example embodiment 1-3 ofthe present invention.

FIG. 9A and FIG. 9B are diagrams illustrating example embodiment 1-4 ofthe present invention.

FIG. 10 is a diagram illustrating example embodiment 2 of the presentinvention.

FIG. 11 is a diagram illustrating an example of example embodiment 2 ofthe present invention.

FIG. 12A and FIG. 12B are diagrams illustrating example embodiment 2-1of the present invention.

FIG. 13A and FIG. 13B are diagrams illustrating example embodiment 2-2of the present invention.

FIG. 14A and FIG. 14B are diagrams illustrating example embodiment 2-3of the present invention.

FIG. 15A and FIG. 15B are diagrams illustrating example embodiment 2-4of the present invention.

FIG. 16 is a diagram illustrating example embodiment 3 of the presentinvention.

FIG. 17A to FIG. 17D are diagrams illustrating example embodiment 4 ofthe present invention.

FIG. 18A to FIG. 18D are diagrams illustrating example embodiment 5 ofthe present invention.

FIG. 19A and FIG. 19B are diagrams illustrating an MVNO of L3connection.

FIG. 20A and FIG. 20B are diagrams illustrating an MVNO of L2connection.

DETAILED DESCRIPTION

The following describes example embodiments of the present invention.

According to one aspect of the present invention, a service is providedto a user of an MNO or MVNO carrier by using a virtual networkfunction(s) (VNFs) each configured by virtualizing a part or all of afunction of a network appliance, a node, and so forth on a serverapparatus.

First, a technology of network function virtualization, which is apremise of the present invention, will be briefly described. In NFV(Network Functions Virtualization) which is a technology thatvirtualizes a network function, a network function is implemented, interms of software, by an application (VNF) that runs on a virtualmachine (VM) on a virtualization layer such as a hypervisor or a virtualmachine monitor (VMM) of a server apparatus. For example, a function ofa dedicated apparatus (a node of the EPC such as an MME, a PGW, or aSGW) can be implemented as a VNF that runs on a VM(s) on avirtualization layer. Hardware resources such as computing, storage, andnetworking, and a virtualization layer of a server apparatus constitutean NFVI (Network Functions Virtualization Infrastructure) serving as aVNF execution infrastructure. As management entities for controlling theNFVI and VNF, a VIM (Virtualized Infrastructure Manager) and a VNFM(Virtual Network Function Manager) are provided. In addition, as a nodethat manages a network service as a whole, an NFVO is included (forexample, reference may be made to NPL 1).

According to one aspect of the present invention, an allocationapparatus (111 in FIG. 1A), performs control such that, depending on towhich carrier or user traffic to be transferred to a VNF belongs, avirtual machine realizing the VNF or a dedicated apparatus (120 in FIG.1A) is allocated as a forwarding destination of the traffic. Namely, theallocation apparatus controls the allocation of the VNF (VM) or thededicated apparatus (120 in FIG. 1A) as a forwarding destination,according to a service level that is set with respect to at least one ofa carrier (for example, an MNO or MVNO carrier), a user, contents of thetraffic, and the like. Alternatively, the allocation apparatus maydetermine the allocation of a VNF as a forwarding destination, based ona type of a user terminal (mobile terminal) which is a transmissionsource or destination of the traffic.

The allocation apparatus (111 in FIG. 1A) may control the allocation oftraffic to a VNF on a per virtual machine (VM) basis, on which the VNFruns. In this case, for example, a plurality of groups, each of whichincludes at least one virtual machine (VM), in correspondence withfunctions, are arranged (in this case, for example, VNFs that operate onthe virtual machines (VMs) in the same group provide the same function).The allocation apparatus may select one of the plurality of groups andselect a virtual machine from the group in accordance with apredetermined scheduling algorithm (for example, in a random schedulingin which a virtual machine is randomly allocated or in a round-robinscheduling in which a virtual machine is sequentially allocated). Next,the allocation apparatus may set the selected virtual machine to anallocation target of the traffic.

The allocation apparatus (111 in FIG. 1A) may be configured to hold acorrespondence between a VNF and a virtual machine (VM) that realizesthe VNF in a table or the like and to forward traffic to a virtualmachine (VM), on which runs the VNF which is a allocation target of thetraffic. In addition, for example, as in the case wherein a single VNFis composed by a combination of a plurality of VNFCs (Virtual NetworkFunction Components) and the plurality of VNFCs correspond to aplurality of virtual machines (VMs), there is a case wherein a singleVNF is executed by a plurality of virtual machines (VMs). In this case,the allocation apparatus (111 in FIG. 1A) may be configured to store andhold in advance a correspondence between a VNF and a virtual machine(VM) of a traffic forwarding destination, out of a plurality of virtualmachines (VMs) which executes the VNF.

Alternatively, the allocation apparatus (111 in FIG. 1A) may setidentification information of a traffic allocation destination VNF (oridentification information of a VDU (Virtual Deployment Unit)) in anunused region in a header of a packet to be forwarded (for example, in aunused field such as bit fields of TOS (Type of Service) or flags in anIP header) and may forward the identification information to a serverapparatus (100 in FIG. 1A). A control unit (a hypervisor, for example)of the server apparatus (100 in FIG. 1A) may analyze, for example, aheader of the packet, and may determine a forwarding destination VNF ofthe packet to forward the packet to the VNF via a virtual switch(vSwitch) or the like, that realizes the VNF.

Alternatively, traffic allocation may be controlled on a per serverapparatus (physical server) basis, on which a VNF is arranged. In thiscase, the allocation apparatus (111 in FIG. 1A) may be configured tostore and hold in advance a correspondence between a VNF and a serverapparatus (server apparatus of a traffic forwarding destination) onwhich the VNF is arranged.

In addition, when the traffic allocation destination is controlled on aper server apparatus (physical server) basis, for example, there may bearranged a plurality of groups, each of which includes one or aplurality of server apparatuses, in correspondence with functions (inthis case, the server apparatuses in the same group provide the samefunction). First, one of the plurality of groups may be selected, andthen, one of the server apparatuses may be selected from the group inaccordance with a predetermined scheduling algorithm (for example, in arandom scheme or a round-robin scheme).

Referring to FIG. 1A, the server apparatus (physical server) 100includes a control unit 101, a plurality of virtual machines (VMs) 102,and a plurality of VNFs 103. For example, a plurality of VNFs 103 (VNF1B, VNF 1C) may be the same kind of virtual network function withdifferent performance. In this specification, for example, in “VNF 1A,”“VNF 1B,” “VNF 1C,” etc., “1” represents a function and “A,” “B,” and“C” represent performance classes. Though not particularly limitedthereto, a VNF 103 may be obtained by virtualizing a network apparatusor a part thereof. For example, VNFs 103B and 103C may be obtained byvirtualizing a part or the whole of a function such as a PGW in the MVNOnetwork 3 in FIG. 20B and implementing the virtual function as anapplication software that runs on the corresponding virtual machine(VM). In this case, for example, the dedicated apparatus 120 may beconfigured by a PGW (a Non-NFV: an apparatus or a node that is not a VNFobtained by virtualizing a network function). Alternatively, a part orthe whole of a function such as a router in the MVNO network 3 in FIG.19B or a server not illustrated may be virtualized, and the virtualfunction may be implemented as an application software that runs on avirtual machine (VM). For example, the number of VNFs 103 is notparticularly limited. A plurality of dedicated apparatuses 120 may bearranged.

The control unit 101 of the server apparatus (physical server) 100includes a virtualization layer such as a hypervisor that virtualizeshardware resources (HW) 104 such as a CPU (Central Processing Unit), amemory such as a RAM (Random Access Memory), a storage such as an HDD(Hard Disk Drive), and a network interface controller (NIC) and thatallocates the virtualized hardware resources to the virtual machine(s)(VM(s)).

FIG. 1A illustrates an example in which the control unit 101 includes avirtual switch (vSwitch) as virtual hardware, only for ease ofexplanation. For example, when the control unit 101 and the hardwareresources (HW) 104 comply with the standard specification of NFV, thecontrol unit 101 and the hardware resources (HW) 104 form an NFVI thatprovides a virtualization infrastructure for executing a virtualmachine(s) (VM(s)) for a VNF(s). For example, regarding setting of avirtual machine(s) (VM(s)), instantiation, termination, scaling,updating and so forth of a VNF, an NFVI is controlled by a VIM(Virtualization Infrastructure Manager) of a NFV-MANO (Management andOrchestration) (not illustrated).

For example, a VNF 1A (not illustrated) is of a high function(performance) type, the VNF 1B 103B is of a medium (standard) function(performance) type, and the VNF 1C 103C is of a low function(performance) type, though not particularly limited thereto. Byperforming registration of a VNF package (on-boarding VNF Package) orupdating on an NFV management apparatus (NFV-MANO (including an NFVOrchestrator (NFVO), a VNF Manager (VNFM), and a VIM)), from amaintenance terminal, an OSS (Operations Support Systems), or the like(not illustrated), setting or updating of a VM image (an image file of avirtual machine VM) corresponding to a VNF is performed. For example,the processing performance of a VNF is controlled by the number ofvirtual CPUs (vCPUs) allocated to a virtual machine (VM) on which theVNF runs, a virtual memory capacity, the number of virtual NICs and abandwidth thereof, a virtual storage capacity and so forth. These areset by definition information of a VNF descriptor that is referred towhen instance information about a VNF or the like is generated by theNFV Orchestrator (NFVO) (reference may be made to NPL 1, for details).

In the example illustrated in FIG. 1B, while the service level of acarrier A (an MVNO carrier) is a first service level (high speed, highquality), it is an expensive contract. The carrier A may be an MNOcarrier that possesses communication facilities including the dedicatedapparatus 120. Alternatively, the carrier A may be an MVNO carrier thatpossesses the dedicated apparatus 120. The service level of a carrier C(an MVNO carrier) is a third service level (low speed, low quality). Theservice level of a carrier B (an MVNO carrier) is a second servicelevel, which is between the first and third service levels.

In this case, the allocation apparatus 111 allocates traffics of thecarriers A, B and C to the dedicated apparatus 120, the VNF 1B, and theVNF 1C, respectively.

Namely, the traffics of the carriers A, B and C (the traffic from theterminals having contracts with the carriers A, B, and C, respectively)are forwarded from the allocation apparatus 111 to the dedicatedapparatus 120 and virtual machine (VMs) that realize VNF 1B and VNF 1C,respectively, and processed by the respective dedicated apparatus 120,VNF 1B, and VNF 1C.

When traffic is forwarded to a virtual machine that realizes a VNF, forexample, a frame (a packet) received by the NIC or the like of theserver apparatus 100 is transmitted to a virtual machine (VM) thatrealizes the corresponding VNF via the virtual switch (vSwitch) or thelike. Packet (frame) data from a VNF may be forwarded to a router in theMVNO network via the virtual switch, the NIC, etc. of the serverapparatus 100 and is next forwarded to a destination via a packet datanetwork or the like such as the Internet or an IMS network.

According to one mode of the present invention, the allocation oftraffic to a VNF that processes the traffic is controlled for eachcarrier corresponding to a service level. Namely, for example, dependingon the carrier, the allocation apparatus 111 in FIG. 1A changes theallocation destination of a user traffic among the dedicated apparatus120, and the VNF 103B to the VNF 103C. For example, when the carrier Ais an MNO lending its communication facilities to an MVNO carrier, theuser traffic of the MNO carrier A is allocated to the dedicatedapparatus 120 or a high-performance (or the highest-performance) VNFamong the plurality of VNFs having the same function.

The service levels in FIG. 1B are simply for the purpose of description.The number of service levels is, as a matter of course, not limited tothree. In addition, for finer classification, a granularity of theservice level may be increased in view of, for example, a relationshipbetween a combination of communication speed (bandwidth) (downlinkspeed), QoS (Quality of Service) and a contract price. For example, thefollowing service levels may be set on a per carrier basis:

high speed and high quality: high price;

high speed and medium quality: relatively high price;

medium speed and medium quality: medium price;

medium speed and low quality: medium price;

low speed and medium quality: relatively low price; and

low speed and low quality: low price.

In this case, the allocation apparatus 111 may allocate traffic to ahigh-performance VNF among the plurality of VNFs having the samefunction or the dedicated device 120 for a MVNO carrier of thehigh-price contract among MVNO carriers. On the other hand, in the caseof a MVNO carrier with a low-price contract, traffic may be allocated toone with lower performance among a plurality of VNFs having the samefunction.

When traffic allocation is performed on a per carrier basis, traffics ofterminals of a plurality of subscribers of the same carrier areallocated to the same allocation destination. Alternatively, as will bedescribed in example embodiments below, an allocation of traffic to aVNF may be performed on a per user basis, instead of on a per carrierbasis. In the case where an allocation of traffic to a VNF on a per userbasis is performed, for example, even if subscribers belong to the samecarrier, a service level is set on a per subscriber (user) depending ona contract or the like thereof. As a result, there may be a case whereintraffics of a plurality of subscribers of the same carrier (for example,users of an MVNO) are allocated to different VNFs or to the dedicatedapparatus 120.

In addition, in FIG. 1A, a plurality of virtual machines (VMs) on whicha plurality of VNFs run may be mounted on different server apparatuses,respectively, and an allocation of traffic to a VNF may be performed ona per server basis or on a per user basis.

According to one mode of the present invention, more flexible controlcan be performed by controlling the allocation of a VNF on a per carrierbasis or on a per user basis, and effective utilization of resources canbe achieved

FIG. 2A schematically illustrates an example of a configuration of theallocation apparatus 111 in FIG. 1A. The allocation apparatus 111includes a control unit 112, a processing unit 113, and a storage unit114. FIG. 2B schematically illustrates information stored in the storageunit 114.

The control unit 112 of the allocation apparatus 111 refers to terminalidentification information (address information) included in a header ofa received packet, identifies a terminal that has transmitted thepacket, and controls the processing unit 113 so as to forward the packetto a virtual machine that realizes a VNF corresponding to the terminal.

The processing unit 113 of the allocation apparatus 111 sets an address(for example, a MAC (Media Access Control) address) of the dedicatedapparatus 120 in a header of a packet (frame) transmitted from theterminal as information about the transmission destination, undercontrolled of the control unit 112. Alternatively, when the allocationapparatus 111 transmits a packet (frame) to an allocation destinationVNF, the processing unit 113 may set identification information of avirtual machine (VM) that realizes the VNF (for example, a host name ofthe virtual machine, an IP/MAC address of the corresponding virtual NIC(vNIC), etc.), or, may transmit the packet (frame) to a transmissionport destined to the destination virtual machine.

For example, as illustrated in FIG. 2B, the storage unit 114 of theallocation apparatus 111 stores correspondence between terminalidentification information (for example, an address, etc.) and anallocation destination VNF as a table structure. Regarding thecorrespondence between the terminal identification information(addresses) and the allocation destination VNFs stored in the storageunit 114, the following variation is possible. For example, when attachprocessing or the like in which a terminal performs registration on anetwork via a base station is performed, for example, based on user'scontract information stored in an HSS or the like, as needed, thecontrol unit 112 may associate a carrier (MNO/MVNO), with which theterminal has a contract, with the terminal identification information(address) of the terminal and store a correspondence between theterminal identification information (address) and an allocationdestination VNF corresponding to the carrier in the storage unit 114.The allocation apparatus 111 may perform processing for storing terminalidentification information (address) and an allocation destination VNFin the storage unit 114, when an EPS (Evolved Packet System) session isestablished after authentication by an MME in the above attachprocessing. A session creation request (Create Session Request) istransmitted from an MME to an SGW, and the session creation request(Create Session Request) is transmitted from the SGW to a PGW. As aresult, a tunnel is established between the SWG and the PGW. An attachrequest message transmitted from the terminal to the MME includes IMSI(International Mobile Subscriber Identity), which is subscriberidentification information, and the session creation request (CreateSession Request) message transmitted from the MME to the SGW and fromthe SGW to the PGW includes IMSI. For example, the allocation apparatus111 may capture this session creation request message to acquire IMSI.In addition, the allocation apparatus 111 refers to contract informationor the like of the subscriber from an HSS and determines a carrier(MNO/MVNO carrier, for example) with which the subscriber has acontract. The allocation apparatus 111 may determine the allocationdestination VNF of a terminal traffic (data traffic, for example) on aper carrier basis, based on an allocation rule. For example, based onthe allocation rule, the allocation apparatus 111 may determine thededicated apparatus to be the allocation destination, when the carrieris an MNO or an MVNO with a high-price contract, while the allocationapparatus 111 may determine the VNFC or VNFB to be the allocationdestination, when the carrier is an MVNO with a low-price contract or amedium-price contract. Alternatively, the allocation apparatus 111 mayrefer to service contract information in an SPR (Service ProfileRepository) from IMSI to determine the traffic allocation destination ona per user basis, based the service contract of the subscriber (user).Alternatively, the MME or the like may determine an allocationdestination of a terminal traffic (data traffic, for example) fromcontract information or the like of the subscriber from the HSS, basedon IMSI to notify the allocation apparatus 111 of the determinedallocation destination. Since the storage unit 114 stores an IP addressof the terminal and the allocation destination VNF in association witheach other, the allocation apparatus 111 can determine the forwardingdestination VNF of a relevant packet by using, for example, an IPaddress in a packet header, as the terminal identification information.In addition, the allocation apparatus 111 may hold a correspondencebetween the VNF and identification information of a server apparatus inwhich the VNF is arranged, or a virtual machine (VM) that realizes theVNF (for example, a host name, or an IP/MAC (Media Access Control)address of a virtual NIC (vNIC)), as a correspondence between terminalidentification information (address) and an allocation destination VNF(a packet forwarding destination VNF) that corresponds to the carrier.

With this configuration, a forwarding destination (a dedicated apparatusor a VNF) of a packet forwarded from a terminal after connection of theterminal is established, is determined based on transmission sourceaddress information (source IP address: IP address of the terminal)extracted from a header of the packet, and the correspondence betweenthe terminal address and the allocation destination stored in thestorage unit 114, and the packet is forwarded by the processing unit 113to the dedicated apparatus 120, or, a server apparatus or a virtualmachine (VM) on which the corresponding VNF runs. The processing unit113 may be configured as a switch including an input port and aplurality of output ports. In the following, a description will be madeat first to an example in which a traffic allocation destination isselected from a plurality of VNFs

Example Embodiment 1

FIG. 3 illustrates a configuration according to example embodiment 1. Aterminal 1 and a base station (eNB) 20 in FIG. 3 are the same as thosedescribed with reference to FIG. 20A and so forth. In FIG. 3 , while anSGW 30 has the same basic configuration as that described with referenceto FIG. 20A and so forth, the SGW 30 includes the function of theallocation apparatus 111 described with reference to FIG. 1 and FIG. 2 .

In FIG. 3 , the terminal 1 (mobile terminal) wirelessly connects to thebase station (eNB) 20 to establish a network connection and connects toa destination node (a node (not illustrated) in the Internet 40 in FIG.20A, for example).

In example embodiment 1, VNF 1A to VNF 1C, each of which has the samefunction and different performance, are implemented on serverapparatuses 100A to 100C, respectively, and an allocation of traffic toa VNF is controlled on a per server apparatus (physical server) basis.VNF 1A to VNF 1C implemented on the server apparatuses 100A to 100C mayrealize a part or all of the functions of a PGW (for example, see FIG.19B or FIG. 20B) or realize a firewall, a load balancer, or, otherserver function, though not limited thereto.

A performance of the server apparatus 100A is relatively high, and aperformance of the server apparatus 100C is relatively low (theperformance of the server apparatus 100C is lower than that of theserver apparatus 100A). In addition, one or a plurality of serverapparatuses 100B (not illustrated) whose performance is between theperformance of the server apparatus 100A and the performance of theserver apparatus 100C may be arranged between the server apparatus 100Aand the server apparatus 100C. The number of server apparatuses is notparticularly limited.

In FIG. 3 , the SGW 30 selects. on a per carrier basis (for example,MVNO, MNO and MVNO), a server apparatus on which a corresponding VNF isarranged (wherein a virtual machine (VM) on which a VNF runs, isarranged on the server apparatus). The SGW 30 forwards traffic to aserver apparatus on which a VNF allocated as a destination is arranged(one of the server apparatuses 100A to 100C). The server apparatusforwards a received traffic via a hypervisor or the like providedthereon to the virtual machine (VM) on which the VNF runs.

The SGW 30 includes the function of the allocation apparatus 111described with reference to FIG. 2 . The SGW 30 allocates trafficcorresponding to an MNO or a high price MVNO carrier to the VNF 1Ainstalled in the high-performance server apparatus 100A. As will bedescribed in an example below, the SGW 30 may allocate trafficcorresponding to the high-price-contract MVNO carrier to a dedicatedapparatus (using no NFV). Traffic of a user of a carrier including adedicated apparatus may be allocated to the dedicated apparatus.

The SGW 30 allocates traffic corresponding to a low-price-contract MVNOcarrier to a general-purpose server (a general-purpose server on which aplurality of VNFs are provided in a mixed manner: a processingperformance of each VNF is low), or the VNF 1C included in thelow-performance server apparatus 100C.

Alternatively, in FIG. 3 , the SGW 30 may allocate traffic to a VNF on aper user basis. Namely, the SGW 30 may allocate traffic of a user whoseservice class is high to the VNF 1A installed in the high-performanceserver apparatus 100A. It is noted that the SGW 30 may allocate trafficto a dedicated apparatus (using no NFV) on a per user basis. Namely, theSGW 30 may allocate traffic of a user whose service class is low to theVNF 1C installed in the low-performance server apparatus 100C.

Alternatively, for example, among a plurality of users having theircontracts with the same carrier, traffic of a user having a high-pricecontract may be allocated to the VNF 1A installed in thehigh-performance server apparatus 100A, while traffic of a user having alow-price contract may be allocated to the VNF 1C installed in thelow-performance server apparatus 100C.

In the example embodiment 1, the allocation of a VNF is controlled on aper server apparatus basis. In addition, the VNF to which traffic isallocated is determined per carrier or per user. Thus, since it is onlynecessary to select a server apparatus including the VNF determined percarrier or per user, the allocation control, etc. are simplified.

As a variation of example embodiment 1, a plurality of serverapparatuses may be divided into groups to form server apparatus groups.In this case, for example, the server apparatus groups may be configuredby dividing a plurality of server apparatuses into a plurality of groupsaccording to function or the like (for example, the grouping may beperformed so that a plurality of server apparatuses having the samefunction belong to the same group).

In this variation, when the SGW 30 selects a server apparatus to whichtraffic is allocated, the SGW 30 may, at first, select one of theplurality of server apparatus groups, according to a service level.Next, from the selected server apparatus group, the SGW 30 may selectone of the server apparatuses and allocate the traffic to the selectedserver apparatus. The selection of a server apparatus in a group may beperformed randomly. Alternatively, the previously selected serverapparatus may be selected continuously (a previously (last) allocatedserver apparatus is re-selected, and as a result, the allocation of thetraffic is continued). Alternatively, the selection of a serverapparatus may be performed in a round-robin scheme or the like. A singleserver apparatus group may include at least one server apparatus. Forexample, when the server apparatuses within the same group provide thesame function, VNFs in one or more server apparatuses within the samegroup have the same function (Network Function). The plurality of serverapparatus within the same group may have different performances (theserver apparatuses in the same group may have the same function butdifferent performances) or may have the same performance (all serverapparatuses in the same group may have the same function and the sameperformance).

For example, a plurality of server apparatus groups (groups A, B and C),each of which has a different performance class, may be provided incorrespondence with a plurality of carriers (carriers A, B and C). Inaccordance with a carrier (for example, carrier A) with which asubscriber has a contract, one (for example, group A) of the pluralityof server apparatus groups is selected and then out of the selectedserver apparatus group (for example, group A), one server apparatuscorresponding to a performance according to content of the contract ofthe subscriber is selected.

Another Example of Allocation

For example, a M2M (Machine to Machine) terminal is assumed to have,

small amount of communication; and

small communication frequency.

Thus, it can be said that no particular problems will occur even iftraffic of an M2M terminal is cased to flow through a path with lowthroughput. For this reason, when the terminal 1 is an M2M terminal inFIG. 3 , traffic of the M2M terminal is allocated to the VNF 1C in thelow-performance server apparatus 100C. In this case, for example, whenthe M2M terminal established connection by (when attach processing isperformed), the traffic from the M2M terminal may be allocated to theVNF 1C of the low-performance server apparatus 100C on a per packetbasis, from correspondence between a type of the M2M terminal and anaddress information of a transmission source of a packet, based onterminal information (terminal identification information, a terminaltype, etc.) acquired by the eNB 20.

Traffic from a mobile terminal or the like, other than the M2M terminalsis allocated to the VNF 1A 103A installed on the high-performance serverapparatus 100A. The reason for this is that since a mobile terminal suchas a smartphone has communication amount larger than an M2M terminal andhas communication frequency higher the M2M terminal (a largercommunication amount and higher communication frequency, by downloadingof a moving picture to the terminal 1, Twitter (a trademark or aregistered trademark by Twitter, Inc.), Facebook (a registered trademarkby Facebook, Inc.), etc.), the traffic from a mobile terminal is causedto flow through a path with higher throughput. A Traffic (downlinkpacket) addressed to the terminal 1 from a communication partner of theterminal 1 (a node connected to a packet data network such as theInternet or an IMS) is forwarded to a VNF (that virtually realizes a PGWfunction, for example) on a server apparatus allocated in correspondencewith the carrier to which the terminal 1 subscribes, via a router(switch), etc. (for example, a Router on the MVNO network in FIG. 20B).Next, the traffic is transmitted from the VNF to the terminal 1 via theSGW 30 and the eNB 20. In this case, the router (switch), etc. may holdcorrespondence between terminal identification information and anallocation destination VNF as illustrated in FIG. 2B and forward apacket (downlink packet) addressed to the terminal 1 to a serverapparatus on which a corresponding allocation destination VNF isarranged. VNFs 103A to 103C on the server apparatuses 100A to 100C inFIG. 3 each may, as a matter of course, be a VNF that processes only anuplink traffic in one direction from the terminal 1, such as a firewallfunction (a packet filter) that controls passage permission of a packetin an uplink direction from the terminal 1 (in this case, a packetaddressed to the terminal 1 (downlink packet) is not forwarded to theVNF).

Example of Example Embodiment 1

FIG. 4 illustrates an example of example embodiment 1 in FIG. 3 . InFIG. 4 , illustration of the terminal 1 and the base station (eNB) 20 inFIG. 3 is omitted. In the example in FIG. 4 , a switch (physical switch)110 selects one of the server apparatuses 100A to 100C. In this case,the SGW 30 and the switch 110 correspond to the allocation apparatus 111in FIG. 1A.

In FIG. 4 , from the server apparatuses 100A to 100C, the SGW 30 selectsa server apparatus on which is arranged a destination VNF to whichtraffic is allocated on a per carrier basis or on a per user basis. TheSGW 30 forwards traffic to the selected server apparatus via the switch110. The SGW 30 may forward a frame with a header in whichidentification information (for example, a MAC address) of the selectedserver apparatus is set, to the switch 110. The switch 110 manages acorrespondence between a port number and a MAC address of a serverapparatus connected to the port in a table, and forwards the frame to aport connected to a server apparatus which is a forwarding destinationof the frame, based on a destination MAC address of a frame header.

Example Embodiment 1-1

FIGS. 5A and B illustrate example embodiment 1-1. Example embodiment 1-1is a specific example of example embodiment 1. In example embodiment1-1, as in example embodiment 1, the allocation of a VNF is controlledon a per server apparatus (physical server) basis. As illustrated inFIG. 5A, in example embodiment 1-1, the SGW 30 controls allocation oftraffic to a VNF on a per carrier basis, based on a policy set by acontrol apparatus (or an operator) 50. In FIG. 5A, for example, thecontrol apparatus 50 and the SGW 30 realize the function of theallocation apparatus 111 as described with reference to FIG. 1 and FIG.2 .

The SGW 30 forwards traffic to a server apparatus on which is arrangedan allocated VNF. The server apparatus forwards a received traffic to avirtual machine (VM) on which the VNF runs via a hypervisor or the likeprovided on the server apparatus.

FIG. 5B illustrates an example of a policy set by the control apparatus(or the operator) 50. As illustrated in FIG. 5B, traffic is allocated toa VNF, in accordance with a service level set on a per carrier basis.Since a way of allocation is the same as that described with referenceto FIG. 1B, description thereof will be omitted. In the followingexample embodiments, the carrier A may be an MNO or an MVNO. Likewise,the carrier B, etc. are not limited to only MVNOs.

As described above, in example embodiment 1-1, the control apparatus (oroperator) 50 sets a policy in the SGW 30 which performs allocation oftraffic to a VNF according to the service level set on a per carrierbasis. Thus, for example, variably setting (update setting) of a policyto the SGW 30 makes it possible to variably set correspondence among acarrier, a service level, and an allocated VNF. This enables effectiveand appropriate utilization of resources of a server apparatus.

Variation of Example Embodiment 1-1

FIG. 6 illustrates a variation of example embodiment 1-1. In thisvariation, a configuration example in which a PCRF 51 and a PCEF (Policyand Enforcement Function) 52 constitute a control apparatus and a PGW 40performs allocation of traffic will be described. In FIG. 6 , the PCEF52, in cooperation with an OCS (Online Charging System) not illustratedand the PCRF 51, applies a policy to a communication (traffic) thatpasses through the PGW 40. In FIG. 6 , for example, the PCRF 51 and thePGW 40 realize the function of the allocation apparatus 111 describedwith reference to FIGS. 1 and 2 .

The PCEF 52 controls carrier traffic that passes through the PGW 40, forexample, based on a high-speed policy, a low-speed policy, etc. The PCEF52 may be implemented inside the PGW 40.

In the configuration example in FIG. 6 , the PGW 40 may allocate trafficon a per carrier basis. In addition, based on policy control informationsent from the PCRF 51 via a Gxc interface, for example, the PGW 40perform allocation of a VNF on a per server apparatus basis according toa service level of a carrier to select a server apparatus on which isarranged an allocated VNF. In this case, under control of the PCEF 52,for example, the PGW 40 may perform VNF allocation on a per serverapparatus basis, according to a corresponding one of different servicelevels, for each of users who subscribes to the same carrier. Forexample, with respect to a prepaid type charge plan (contract) for auser, the PCRF 51 which has acquired an allowable communication amountfrom an OCS (not shown) which manages communication amount and convertsthe communication amount into a prepaid balance decides the acommunication policy (communication speed), and the PCEF 52 applies thepolicy to a user traffic in the PGW 40. For example, when there is stilla certain communication amount left in a prepaid-type charging plan (forexample, 2 GB (Gigabytes)), the PCEF 52 may apply a high-speedcommunication policy, and the user traffic may be allocated to the VNF1A on the server apparatus 100A. When there is no communication amountleft, for example, the PCEF 52 may perform switching to a low-speedcommunication policy such as 128 kbps (kilo bits per second) at amaximum, and the user traffic may be allocated to the VNF 1C on theserver apparatus 100C. While the PCRF 51 and PCEF 52 in FIG. 6constitute a variation of the control apparatus 50 in FIG. 5 , settingof a policy and a policy based traffic allocation control scheme are notas a matter of course limited to the configuration illustrated in FIG. 6.

Example Embodiment 1-2

FIGS. 7A and 7B illustrate example embodiment 1-2. Example embodiment1-2 is a specific example of example embodiment 1. As in exampleembodiment 1, the SGW 30 allocates traffic to a VNF on a per serverapparatus (physical server) basis.

As illustrated in FIGS. 7A and 7B, in example embodiment 1-2, control oftraffic allocation to VNF on a per user basis (for each terminalidentification information (terminal ID) or address of terminal 1) basedon a policy set from the control apparatus (or operator) 50. As theidentification information of the terminal 1, identification informationsuch as IMSI (International Mobile Subscriber Identity) stored in a SIM(Subscriber Identity Module) card of the terminal 1 and included in anattach request (Attachment request) message transmitted from theterminal 1 to the MME may be used.

As illustrated in FIG. 7A, in example embodiment 1-2, based on a policyset by the control device (or operator) 50, the SGW 30 controls trafficallocation to VNF for each user. The SGW 30 forwards traffic to a serverapparatus on which is arranged an allocated VNF. The server apparatusforwards a received traffic, via a hypervisor or the like on the serverapparatus, to a virtual machine (VM) on which the VNF runs.

FIG. 7B illustrates an example of the policies set by the controlapparatus (or operator) 50. As illustrated in FIG. 7B, the SGW 30controls allocation of traffic to a VNF, in accordance with a servicelevel set on a per user basis (an ID or an address of terminal 1).

In the example in FIG. 7B, the SGW 30 allocates:

traffic from a terminal of a user 1 that subscribes to a carrier A,which is an MNO or MVNO carrier, to a high-speed server apparatus 100Aon which a VNF 1A runs;

traffic from a terminal of a user 2 that subscribes to the carrier A toa medium-speed server apparatus 100B on which a VNF 1B runs; and

traffic from a terminal of a user 3 that subscribes to an MVNO carrier Bto a low-speed server apparatus 100C on which a VNF 1C runs.

As described above, in example embodiment 1-2, the control apparatus (oroperator) 50 sets a policy in the SGW 30, which allocates traffic to aVNF, in accordance with a service level set on a per user basis. Byvariably setting a policy from the control apparatus (or the operator)50, a correspondence among a user, a service level, and an allocationdestination VNF of a user traffic can be variably set. This enableseffective and appropriate utilization of resources of a serverapparatus.

The control apparatus 50 illustrated in FIG. 7A may, as a matter ofcourse, be configured by the PCRF 51 and the PCEF 52 as described withreference to FIG. 6 . In this case, the PCRF 51 may set a policy withreference to a charging rule of a user, for example.

When the terminal 1 is an M2M terminal, a policy corresponding to athird service level in FIG. 7B may be applied, and traffic from the M2Mterminal may be allocated to a low-speed server apparatus 100C on whichis installed the VNF 1C. Traffic (downlink packet) addressed to theterminal 1 from a communication partner of the terminal 1 (a nodeconnected to a packet data network such as the Internet or an IMS) isforwarded to a VNF (that virtually realizes a PGW function, for example)on a server apparatus allocated on a per user basis via a router(switch), etc. (for example, Router on the MVNO network in FIG. 20B).Next, the traffic is transmitted from the VNF to the terminal 1 via theSGW 30 and the eNB 20. In this case, the router (switch), etc. may holda correspondence between a terminal address (user terminal IDs) and anallocation destination VNF as illustrated in FIG. 7B to forward a packet(downlink packet) addressed to the terminal 1 of a corresponding user toa server apparatus in which is provided an allocation destination VNF.It is needless to say that the VNFs 103A to 103C on the serverapparatuses 100A to 100C in FIG. 7A may process only an uplink trafficin one direction from the terminal 1, by using a firewall function(packet filtering) that controls permission to pass a packet from theterminal 1 in an uplink direction (in this case, a packet (downlinkpacket) addressed to the terminal 1 is not forwarded to the VNF).

Example Embodiment 1-3

FIGS. 8A and 8B illustrate example embodiment 1-3. Example embodiment1-3 is a specific example of example embodiment 1. As in exampleembodiment 1, the allocation of traffic to a VNF is controlled on a perserver apparatus (physical server) basis.

As illustrated in FIG. 8A, in example embodiment 1-3, based onsubscriber information or service contract information (change ofcontract: for example, change of charging plan, addition of a prepaidfee, etc.) in an SPR (Subscriber Profile Repository) in an HSS 70, theSGW 30 controls the allocation of traffic to a VNF on a per user basis.The SGW 30 forwards traffic to a server apparatus on which is arrangedan allocated VNF. The server apparatus forwards received traffic to avirtual machine (VM) on which the VNF runs via a hypervisor or the likeon the server apparatus.

In FIG. 8A, an MME 60 performs, for example, authentication of theterminal 1 in coordination with the HSS 70, when attachment processingof the terminal 1 is performed. In an authentication Procedure, IMSI isincluded in an attachment request message transmitted from the terminal1 to the MME 60. The MME 60 transmits an authentication informationrequest including the IMSI and a serving network ID to the HSS 70, andthe HSS 70 creates and transmits an authentication vector to the MME 60.The MME 60 transmits an authentication request to the terminal 1, andthe terminal 1 authenticates the network and transmits an authenticationresponse of the terminal 1 to the MME 60. The MME 60 compares a value(RES) of the authentication response from the terminal 1 with a value(XRES) included in the authentication vector from the HSS 70 anddetermines whether to authenticate the user. After this authentication,the MME 60 may acquire subscriber profile information (service contractinformation, charging information, etc.) in the SPR (Subscriber ProfileRepository) in the HSS 70 by using the IMSI of the terminal 1 anddetermine a user-specific traffic allocation destination VNF on a perserver apparatus basis. Alternatively, after the authentication, the SGW30 may acquire subscriber profile information (service contractinformation, charging information, etc.) of SPR in the HSS 70 by usingthe IMSI or the like included in a session creation request (CreateSession Request) message transmitted from the MME 60 to the SGW 30 anddetermine a user-specific traffic allocation destination VNF on a perserver apparatus basis. Alternatively, for example, based on a servicepolicy (a service policy for a user) determined by a PCRF (notillustrated), the SGW 30 may determine a user-specific trafficallocation destination VNF on a per server apparatus basis.Alternatively, the base station (eNB) 20 may determine a user-specifictraffic allocation destination on a per server apparatus basis. In suchcase, the base station (eNB) 20 may include the allocation apparatus 111described with reference to FIG. 2 .

FIG. 8B illustrates an example in which a VNF is allocated on a per userbasis (for each terminal identification information (terminal ID) oraddress of the terminal 1). Since the allocation in FIG. 8B is the sameas that described with the policies in FIG. 7B (the allocation of a VNFper user), description thereof will be omitted.

In example embodiment 1-3, the setting of the allocation of user trafficto a VNF may be changed, for example, based on service contractinformation (charging information) of a user in the HSS 70 and dependingon the change of the contract of the user (for example: change of achanging plan, addition of a prepaid fee, etc.).

In example embodiment 1-3, for example, according to an increase of amonthly communication capacity due to addition of a prepaid fee, thesetting of the allocation of user traffic to a VNF may be changed (forexample, from a low-performance VNF to a high-performance VNF).

Alternatively, in example embodiment 1-3, with a change of content of aservice contract of a user (upgrading, for example), the setting of theallocation of user traffic to a VNF may be changed in such a manner thatthe user traffic is allocated to a VNF having a further added functionas compared with that of a currently selected VNF (scale-up, scale-out,etc.). Alternatively, with a change of content of the service contractof the user (downgrading, for example), the setting of the allocation ofuser traffic to a VNF may be changed in such a manner that the usertraffic is allocated to a VNF having a function reduced from that of acurrently selected VNF (scale-down, scale-in, etc.).

In addition, in example embodiment 1-3, for example, with anupgrade-change of content of a service contract of a user, a voice callfunction and an SMS (Short Message Service) function may be released. Aservice chain (deployment of a VNF and physical and virtual componentssupporting the VNF) may be reconfigured so that the traffic from theuser is enabled to use a voice call and an SMS. In contrast, with adowngrade-change of content of a service contract of a user, a VNFservice chain may be reconfigured so that a function(s) that has beenset cannot be used.

According to example embodiment 1-3, user traffic can be allocated to aVNF in accordance with content of a service contract of a user. Inaddition, for example, an optimum VNF can be allocated so as to follow achange of content of the service contract.

In example embodiment 1-3, as described in example embodiment 1-2, whenthe terminal 1 is an M2M terminal, traffic from the M2M terminal may beallocated to the low-speed server apparatus 100C on which is arrangedthe VNF 1C in accordance with contract information of the M2M terminal.

Example Embodiment 1-4

FIGS. 9A and 9B illustrate example embodiment 1-4. Example embodiment1-4 is a specific example of example embodiment 1. As in exampleembodiment 1, the allocation of traffic to a VNF is controlled on a perserver apparatus (physical server) basis. As illustrated in FIGS. 9A and9B, in example embodiment 1-4, based on a policy from the controlapparatus 50, the SGW 30 selects a server apparatus on which anallocation destination VNF runs, out of the server apparatuses 100A to100C on which VNFs run, based on contents of traffic or an application.The SGW 30 forwards traffic to a server apparatus on which is arrangedan allocated VNF. The server apparatus forwards received traffic to avirtual machine (VM) on which the VNF runs via a hypervisor or the likeon the server apparatus.

FIG. 9B lists policies as follows:

contents: YouTube (registered trademark) (HD (High Definitiontelevision)) which is high speed, a first service level, and allocationdestination is VNF 1A;

contents: YouTube (registered trademark) (SD (Standard Definitiontelevision)) which is a low-speed, a third service level, and allocationdestination is VNF 1C; and

other video services, a second service level, and allocation destinationis VNF 1B.

For example, content information or the like may be acquired byanalyzing header (HTTP header) information in an HTTP (Hyper textTransport Protocol) request. For example, a URL (Uniform ResourceLocator) of a content delivery source may be acquired from a host field(HTTP 1.1) or the like. Alternatively, a URI (Uniform ResourceIdentifier) indicating a unique location of contents may be acquiredfrom Content-Location of an entity header. In addition, for example, byusing Deep Packet Inspection for analyzing a payload portion of a packetor Stateful Deep Packet Inspection for checking a packet header portion,information on contents or an application may be extracted. Contentinformation acquired may be matched with a policy to select a serverapparatus on which is arranged a virtual machine (VM) realizing atraffic allocation destination VNF.

According to example embodiment 1-4, it is possible to allocate a VNFcorresponding to contents to be forwarded or an application providingcontents.

Example Embodiment 2

FIG. 10 illustrates a configuration according to example embodiment 2.In example embodiment 2, the allocation of a VNF is controlled on a pervirtual machine (VM) basis. For example, a plurality of VNFs (VNF 1A toVNF 1C) having the same function are implemented on separate virtualmachines (VMs) on the same server apparatus. The number of virtualmachines is not particularly limited. In the example in FIG. 10 ,virtual machines (VMs) 102A to 102C implemented on a virtualizationlayer such as a hypervisor (a control unit 101) of a server apparatus100 are provided, and the VNF 1A to VNF 1C run on the respective virtualmachines (VMs) 102A to 102C. In FIG. 10 , an SGW 30 includes thefunction of the allocation apparatus 111 described with reference toFIG. 1A and FIG. 2A.

A processing performance of the virtual machine 102A is relatively high,a processing performance of the virtual machine 102C is relatively low,and a processing performance of the virtual machine 102B not illustratedis a medium processing performance. A performance value of the virtualmachine 102B is, for example, an intermediate value between performancevalues of the virtual machines 102A and 102C.

When the allocation of a VNF is performed on a per MVNO carrier basis,for example, traffic corresponding to a high-price-contract MVNO carrieris allocated to the VNF 1A that runs on a high-performance VM 102A. Incontrast, traffic corresponding to a low-price-contract MVNO carrier isallocated to the VNF 1C that runs on the low-performance VM 102C.

When the allocation of a VNF is performed on a per user basis, based onservice contract information of a user, user traffic of an upper serviceclass is allocated to the VNF 1A that runs on the high-performance VM102A. In contrast, user traffic of a lower service class is allocated tothe VNF 1C that runs on the low-performance VM 102C.

The SGW 30 transmits traffic to the server apparatus 100. In thisoperation, the SGW 30 may set information (identification information orthe like) specifying an allocated VFN in a packet header of the traffic(for example, in an unused bit field in an IP header) and may forwardthe traffic to the server apparatus 100. Alternatively, the SGW 30 mayset a MAC address of a virtual machine (VM) on which an allocated VNFruns (a virtual MAC address allocated automatically in a software-basedmanner by a hypervisor when power-on of a VM is performed) in a frameheader of the traffic and may forward the traffic to the serverapparatus 100.

Among a plurality of VNF 1A to VNF 1C on the server apparatus, theserver apparatus 100 forwards traffic received from the SGW 30 to avirtual machine (VM) on which a VNF allocated by the SGW 30 runs.

According to example embodiment 2, the allocation of a VNF is controlledon a per virtual machine (VM) basis. Thus, as compared with exampleembodiment 1 in which the allocation is controlled on a per serverapparatus basis, example embodiment 2 enables reduction of serverresource (for example, the number of server apparatuses) and thus,operation cost can be reduced.

Example of Example Embodiment 2

FIG. 11 schematically illustrates a configuration example of exampleembodiment 2. In the example in FIG. 11 , a virtual switch (vSwitch) 106in the server apparatus 100 forwards traffic received from the SGW 30 toa virtual machine (VM).

A frame (packet) from a physical NIC 105 is supplied to an input port(U) of the virtual switch 106. For example, the virtual switch 106analyzes a frame header and determines an output port connected to theforwarding destination virtual machine (VM) based on a MAC address of avirtual machine (VM) that is set in a frame header by the SGW 30 oridentification information that is set in a header by the SGW 30 (VNFidentification information set in an unused bit field in a header or thelike). The virtual switch 106 forwards the frame to a correspondingallocated VNF (application) that runs on a guest OS (Operating System)(device driver) via a virtual NIC and the guest OS in the virtualmachine (VM). Data (packet data) processed by and outputted from a VNFis formed, for example, into a frame by a virtual NIC, is thentransmitted via the virtual switch 106 and the physical NIC 105, to aforwarding destination in a MVNO network (the Router in the MVNO networkin FIG. 20B, for example), and then is transmitted to the communicationpartner of the terminal 1 via a packet data network such as the Internetor the IMS. In FIG. 11 , the virtual switch (vSwitch) 106 and the SGW 30in FIG. 10 may constitute the allocation apparatus 111 in FIG. 1A.Though not particularly limited thereto, when a single VNF are realizedby a plurality of virtual machines (VMs), among the plurality of VNFCs(VNF Components) constituting the VNF, traffic is forwarded to a virtualmachine (VM) that realizes a VNFC connected to a virtual NIC (virtualnetwork: external link).

Example Embodiment 2-1

FIGS. 12A and 12B illustrate example embodiment 2-1. Example embodiment2-1 is a specific example of example embodiment 2. As in exampleembodiment 2, the allocation of a VNF is controlled on a per virtualmachine (VM) basis.

As illustrated in FIG. 12A, in example embodiment 2-1, based on a policyset by a control apparatus (or operator) 50, the SGW 30 controls theallocation of traffic to a VNF for each carrier on a per virtual machine(VM) basis. The SGW 30 sets identification information (for example, avirtual MAC address) of a virtual machine (VM) in header information ofa frame or packet so that the traffic is forwarded to the virtualmachine (VM) on which an allocated VNF runs and forwards the traffic tothe server apparatus 100. The server apparatus 100 forwards the trafficto the destination VNF, as described with reference to FIG. 11 .

FIG. 12B illustrates an example of a policy set by the control apparatus(or the operator) 50. As illustrated in FIG. 12B, in accordance with aservice level set on a per carrier basis, the SGW 30 controls theallocation of traffic to a VNF. Since a way of the allocation is thesame as that described with reference to FIG. 5B, description thereofwill be omitted.

In example embodiment 2-1, based on a policy set in the SGW 30 by thecontrol apparatus (or operator) 50, the allocation of a VNF inaccordance with a service level set on a per carrier basis is performed.By variably setting a policy from the control apparatus (or operator)50, it is made possible to set variably a correspondence among an MVNOcarrier, a service level, and a VNF. This enables effective andappropriate utilization of server resources.

In example embodiment 2-1, as in the variation of example embodiment 1-1(see FIG. 6 ), the SGW 30 may allocate traffic to a virtual machine(group) on a per carrier basis, and the PGW 40 may perform theallocation of a VNF on a per virtual machine basis, in accordance with aservice level, for the same carrier, based on policy control informationor the like transmitted from a PCRF 51 via a Gxc interface.

Example Embodiment 2-2

FIGS. 13A and 13B illustrate example embodiment 2-2. Example embodiment2-2 is a specific example of example embodiment 2. As in exampleembodiment 2, the allocation of a VNF is controlled on a per virtualmachine (VM) basis.

As illustrated in FIGS. 13A and 13B, in example embodiment 2-2, based ona policy set by the control apparatus (or the operator) 50, the SGW 30controls the allocation of traffic to a VNF on a per user basis (basedon terminal identification information (a terminal ID) or an address ofthe terminal 1). As the identification information of the terminal 1,IMSI (International Mobile Subscriber Identity) stored in a SIM(Subscriber Identity Module) card of the terminal may be used. The SGW30 sets identification information of a virtual machine on which anallocated VNF runs (for example, a virtual MAC address) in headerinformation of a frame or packet so that the traffic is forwarded to thevirtual machine (VM) and forwards the traffic to the server apparatus100. The server apparatus 100 forwards the traffic to the destinationVNF, as described with reference to FIG. 11 .

As illustrated in FIG. 13A, in example embodiment 2-2, based on a policyset by the control apparatus (or operator) 50, the allocation of trafficto a VNF is performed for each user. FIG. 13B illustrates an example ofa policy set by the control apparatus (or operator) 50. As illustratedin FIG. 13B, the allocation of traffic to a VNF is controlled inaccordance with a service level set for each user (an ID or an addressof the terminal 1). In the example in FIG. 13B:

traffic from a terminal of a user 1 that subscribes to a carrier A (MNOor MVNO) to a high-speed VM 102A on which a VNF 1A runs;

traffic from a terminal of a user 2 that subscribes to the carrier A(MNO or MVNO) to a medium-speed VM 102B on which a VNF 1B runs; and

traffic from a terminal of a user 3 that subscribes to the carrier B (anMVNO carrier) to a low-speed VM 102C on which a VNF 1C runs.

In FIG. 13A, the control apparatus (or operator) 50 and the SGW 30realize the function of the allocation apparatus 111 described withreference to FIG. 1A and FIG. 2A.

In example embodiment 2-2, based on a policy set in the SGW 30 by thecontrol apparatus (or operator) 50, the allocation of traffic to a VNFis performed in accordance with a service level set for each user.According to example embodiment 2-2, by variably setting a policy fromthe control apparatus (or operator) 50, it is made possible to setvariably a correspondence among a user, a service level, and a VNF. Thisenables effective and appropriate utilization of server resources, VMresources in particular.

In example embodiment 2-2, as in example embodiment 1-2, when theterminal 1 is an M2M terminal, a policy corresponding to a third servicelevel in FIG. 13B may be applied, and traffic from the M2M terminal maybe allocated to a low-speed VNF 1C.

Example Embodiment 2-3

FIGS. 14A and 14B illustrate example embodiment 2-3. Example embodiment2-3 is a specific example of example embodiment 2. As in exampleembodiment 2, the allocation of traffic to a VNF is controlled on a pervirtual machine (VM) basis.

As illustrated in FIG. 14A, in example embodiment 2-3, based onsubscriber information (for example, change of content of a servicecontract (for example: change of a charging plan, addition of a prepaidfee, etc.)) in an HSS 70, the allocation of traffic to a VNF iscontrolled on a per user basis.

In FIG. 14A, an MME 60 performs, for example, authentication incoordination with the HSS 70, when attachment processing of the terminal1 is performed. The MME 60 may refer to subscriber profile information(service contract information, charging information, etc.) in the HSS 70to determine a traffic allocation destination VNF based on thesubscriber profile information. The SGW 30 receives a notification(allocation destination VNF) from the MME 60 or the base station 20,sets identification information (for example, a virtual MAC address,etc.) of a virtual machine (VM) on which the allocated VNF runs, inheader information of a frame or packet so that the traffic is forwardedto the virtual machine (VM), and forwards the traffic to the serverapparatus 100. The server apparatus 100 forwards the traffic to thedestination VNF as described with reference to FIG. 11 .

In the present example embodiment, the base station 20 may determine auser-specific traffic allocation destination VNF on a per virtualmachine (VM) basis.

FIG. 14B illustrates an example in which a VNF is allocated on a peruser basis (per terminal identification information (terminal ID) oraddress of the terminal 1). Since the allocation in FIG. 14B is the sameas that described with the policies in FIG. 8B (the allocation of a VNFper user), description thereof will be omitted.

In example embodiment 2-3, with a change of contract information of auser (for example, change of a charging plan or addition of a prepaidfee), the setting of the allocation of user traffic to a VNF may bechanged, for example.

In example embodiment 2-3, for example, with an increase of a monthlycommunication capacity by addition of a prepaid fee, the setting of theallocation of user traffic to a VNF may be changed (for example, from alow-performance VNF to a high-performance VNF).

Alternatively, in example embodiment 2-3, with a change of content of acontract (upgrading, for example), the setting of the allocation of usertraffic to a VNF may be changed in such a manner that the user trafficis allocated to a VNF having a further added function as compared withthat of a currently selected VNF. Alternatively, with a change ofcontent of the contract (downgrading, for example), the setting of theallocation of user traffic to a VNF may be changed in such a manner thatthe user traffic is allocated to a VNF having a function reduced fromthat of a currently selected VNF.

In addition, in example embodiment 2-3, for example, with anupgrade-change of content of a contract of a user, a voice call functionand an SMS (Short Message Service) function may be released. A servicechain (deployment of a VNF and physical and virtual componentssupporting the VNF) may be reconfigured so that the traffic of the useris enabled to use a voice call and an SMS. In contrast, with adowngrade-change of content of a service contract of a user, a VNFservice chain may be reconfigured so that a function(s) that has beenset cannot be used.

According to example embodiment 2-3, user traffic can be allocated to aVNF in accordance with content of a contract of a user. In addition, forexample, an optimum VNF can be allocated so as to follow a change ofcontent of the service contract.

In example embodiment 2-3, as in example embodiment 2-2, when theterminal 1 is an M2M terminal, traffic from the M2M terminal may beallocated to the low-speed VNF 1C in accordance with contractinformation of the M2M terminal.

Example Embodiment 2-4

FIGS. 15A and 15B illustrate example embodiment 2-4. Example embodiment2-4 is a specific example of example embodiment 2. As in exampleembodiment 2, the allocation of traffic to a VNF is controlled on a perVM basis.

As illustrated in FIGS. 15A and 15B, in example embodiment 2-4, based ona policy from the control apparatus 50, the SGW 30 selects a trafficallocation destination VNF from a plurality of VNFs 1A to 1C arranged inthe server apparatus 100, based on contents of traffic or anapplication. FIG. 15B lists policies as follows:

contents: YouTube (registered trademark) (HD (High Definitiontelevision)) which is high speed, a first service level, and allocationdestination is VNF 1A;

contents: YouTube (registered trademark) (SD (Standard Definitiontelevision)) which is a low-speed, a third service level, and allocationdestination is VNF 1C; and

other video services, a second service level, and allocation destinationis VNF 1B.

The SGW 30 receives a notification (allocation destination VNF) from theMME 60 or the base station 20, sets identification information (forexample, a virtual MAC address, etc.) of a virtual machine (VM) on whichthe allocated VNF runs, in header information of a frame or packet sothat the traffic is forwarded to the virtual machine (VM), and forwardsthe traffic to the server apparatus 100. The server apparatus 100forwards the traffic to the destination VNF as described with referenceto FIG. 11 .

In example embodiment 2-4, as in the above example embodiment 1-4,content information or the like may be acquired by analyzing header(HTTP header) information in an HTTP (Hyper text Transport Protocol)request. For example, a URL (Uniform Resource Locator) of a contentdelivery source may be acquired from a host field (HTTP 1.1) or thelike. Alternatively, a URI (Uniform Resource Identifier) indicating aunique location of contents may be acquired from Content-Location of anentity header. In addition, for example, by using Deep Packet Inspectionfor analyzing a payload portion of a packet or Stateful Deep PacketInspection for checking a packet header portion, information on contentsor an application may be extracted. Content information acquired may bematched with a policy to select a virtual machine (VM) realizing atraffic allocation destination VNF.

According to example embodiment 2-4, for example, it is possible toallocate a VNF corresponding to contents to be forwarded or anapplication providing contents.

Example Embodiment 3

FIG. 16 illustrates a configuration of example embodiment 3. In exampleembodiment 3, too, the allocation of traffic to a VNF is controlled on aper virtual machine (VM) basis.

In the example illustrated in FIG. 16 , a service provided by VNFs (aVNF 1A and a VNF 1B) on a first server apparatus 100D and a serviceprovided by VNFs (a VNF 2A and a VNF 2B) on a second server apparatus100E are different to each other. Namely, while the VNF 1A and the VNF1B are the same function (a first function), VNF 1A and the VNF 1B aredifferent in performance classes. While the VNF 2A and the VNF 2B arethe same function (a second function different from the first function),the VNF 2A and the VNF 2B are different in performance classes.

In the first server apparatus 100D on which are arranged the VNF 1A andVNF 1B providing the first service, a virtual machine VM 1A is ahigh-performance VM, and a virtual machine VM 1B is a low-performanceVM. The VNF 1A on the virtual machine VM 1A is a high-performance VNF,and the VNF 1B on the virtual machine VM 1B is a low-performance VNF. Inthe second server apparatus 100E on which are arranged the VNF 2A andthe VNF 2B providing the second service, a virtual machine VM 2A is ahigh-performance VM, and a virtual machine VM 2B is a low-performanceVM. The VNF 2A on the virtual machine VM 2A is a high-performance VNF,and the VNF 2B on the virtual machine VM 2B is a low-performance VNF.

As described above, in example embodiment 3, a plurality of VNFs, whosequality levels are classified for each service, are arranged to form achaining configuration. A granularity of the classification of thequality level or the like for each VNF may differ between the serverapparatuses 100D and 100E. For example, a service level is divided intoeight levels in the first server apparatus 100D, while a service levelis divided into four levels in the second server apparatus 100E. Namely,the granularity of the service level may differ depending on Qos(Quality of Service), communication speed, contract and so forth.

In example embodiment 3, a hierarchy (rank) of the classification maydiffer depending on a VNF. For example, a high-performance VNF and alow-performance VNF may be arranged in the server apparatus 100D, whilea high-performance VNF, a medium-performance VNF, and a low-performanceVNF may be arranged in the server apparatus 100E.

In example embodiment 3, depending on a VNF, server apparatuses may notbe divided for each service provided by the VNF and a single serverapparatus may provide different services.

In addition, in example embodiment 3, VNFs classified for each serviceand a VNF selecting whether to add a function of the VNF (for example,SMS option) may coexist.

In addition, in example embodiment 3, as described in the above exampleembodiments 1-4, 2-4, etc., based on subscriber information of a user, aVNF to which traffic is allocated may be selected (a server apparatusmay be selected, and a VNF in the server apparatus may be selected).Alternatively, as in the above example embodiments 1-2, 1-3, 2-2, 2-3,etc., based on a set policy, the SGW 30 may select a VNF to allocate(selection of a server apparatus, and selection of a VNF in the serverapparatus selected).

Example embodiment 3 enables fine resource allocation based on acombination of services (functions) provided and a quality, and agranularity for a classification.

Example Embodiment 4

FIG. 17A illustrates a configuration of example embodiment 4. Asillustrated in FIG. 17A, in example embodiment 4, a carrier-gradededicated apparatus 120 and the server apparatuses according to exampleembodiment 1 described with reference to FIG. 3 (the server apparatuses100B and 100C out of the server apparatuses 100A to 100C in FIG. 3 ) areprovided. VNF 1B on the server apparatus 100B is obtained byvirtualizing a function (network function) of the dedicated apparatus120 on the server apparatus 100B and realizes processing and functionthat the dedicated apparatus 120 performs, in a software-based manner ona virtual machine. The dedicated apparatus 120 may be possessed by anMNO or a specific MVNO carrier.

As illustrated in FIG. 17B, for example, when a carrier A is a carrier(MNO or MVNO) that possesses infrastructure such as the dedicatedapparatus 120 or a high-price-contract MVNO carrier, trafficcorresponding to the carrier A is allocated to the dedicated apparatus120. Traffic corresponding to a low-price-contract MVNO carrier B or Cis allocated to the VNF 1B on the server apparatus 100B or the VNF 1C onthe server apparatus 100C.

When allocating user traffic to the dedicated apparatus 120, the SGW 30may set a MAC address of the dedicated apparatus 120 in a frame headerof the traffic and forward the traffic. When allocating traffic to theVNF 1B, the SGW 30 selects the server apparatus 100 on which is arrangedthe VNF 1B (selection on a per server basis). The SGW 30 may setidentification information of a virtual machine (VM) realizing the VNF1B (or identification information of the VNF) in a frame header (packetheader) or the like of the traffic and forward the traffic to the serverapparatus 100B. The server apparatus 100B forwards the traffic to thedestination VNF as described with reference to FIG. 11 .

As a variation of example embodiment 4, the allocation destination oftraffic may be controlled on a per user basis. For example, in theexample illustrated in FIG. 17C, a user 1 of a carrier A corresponds toa first service level, and traffic of the user 1 is allocated to thededicated apparatus 120. A user 2 of the carrier A corresponds to asecond service level, and traffic of the user 2 is allocated to the VNF1B.

Alternatively, in another variation of example embodiment 4, regardingtraffic of users of the same carrier, according to a service levelcorresponding to contents that traffic (traffic destined to a terminal1) carries, a traffic allocation destination may be set to one of thededicated apparatus 120, the VNF 1B, and the VNF 1C. In the exampleillustrated in FIG. 17D, traffic carrying contents of a first servicelevel is allocated to the dedicated apparatus 120.

The dedicated apparatus 120 may be an arbitrary network facility, aserver apparatus, or the like. For example, the dedicated apparatus 120may be a PGW or a server group in FIG. 20B or a router (Router) or thelike in FIG. 19B.

According to example embodiment 4, an existing dedicated apparatus 120(for example, an existing PGW) that does not comply with NFV can be usedtogether with NFV. Thus, example embodiment 4 is very effective as atransitional measure (a system configuration) until network facilitiesare fully virtualized as NFV.

Example Embodiment 5

FIG. 18A illustrates a configuration of example embodiment 5. Asillustrated in FIG. 18A, in example embodiment 5, there are provided adedicated apparatus 120 and a server apparatus 100. The server apparatus100 corresponds to the server apparatus 100 according to exampleembodiment 2 described with reference to FIG. 10 (however, the serverapparatus 100 includes only the VNFs 1B and 1C). In FIG. 18A, each ofthe VNF 1B and the VNF 1C on the server apparatus 100 is obtained byvirtualizing a function of the dedicated apparatus 120 and realizesprocessing and functions of the dedicated apparatus 120 on a virtualmachine in a software-based manner. The dedicated apparatus 120 may bepossessed by an MNO or a specific MVNO carrier. In FIG. 18A, forsimplicity's sake, only one server apparatus is illustrated, but aplurality of server apparatuses may, as a matter of course, be arranged.

As illustrated in FIG. 18B, for example, when a carrier A is a carrier(an MNO or an MVNO) that possesses infrastructure such as the dedicatedapparatus 120 or a high-price-contract MVNO carrier, trafficcorresponding to the carrier A is allocated to the dedicated apparatus120. Traffic corresponding to a low-price-contract MVNO carrier B or Cis allocated to the VNF 1B or the VNF 1C on the server apparatus 100.

When an SGW 30 allocates traffic to the dedicated apparatus 120, forexample, the SGW 30 may set a MAC address of the dedicated apparatus 120in a frame header of the traffic to forward the traffic. When the SGW 30allocates traffic to the VNF 1B, the SGW 30 selects the server apparatus100 on which is arranged the VNF 1B (selection per server). The SGW 30may set identification information of a virtual machine (VM) realizingthe VNF 1B (or identification information of the VNF) in a frame header(a packet header) or the like of the corresponding traffic to forwardthe traffic to the server apparatus 100. The server apparatus 100forwards the traffic to the destination VNF as described with referenceto FIG. 11 .

As a variation of example embodiment 5, as illustrated in FIG. 18C,traffic of a user 1 of the carrier A corresponding to a first servicelevel may be allocated to the dedicated apparatus 120. Namely, theallocation destination of traffic is set on a per user basis.

Alternatively, as another variation of example embodiment 5, asillustrated in FIG. 18D, traffic carrying a content of the first servicelevel may be allocated to the dedicated apparatus 120. Namely, a servicelevel may be set on a per content that traffic (traffic destined to aterminal 1) carries, and the allocation destination of traffic may beset based on the corresponding service level.

The dedicated apparatus 120 may be an arbitrary network facility, or thelike. For example, the dedicated apparatus 120 may be a PGW or a servergroup in FIG. 20B or a router (Router) or the like in FIG. 19B.

According to example embodiment 5, an existing dedicated apparatus 120that does not comply with NFV can be used together with NFV. Thus,example embodiment 5 is very effective as transitional measures (systemconfiguration) until the network facilities are are fully virtualized asNFV.

The disclosure of the above NPL 1 is incorporated herein by referencethereto. Variations and adjustments of the example embodiments andexamples are possible within the scope of the overall disclosure(including the claims) of the present invention and based on the basictechnical concept of the present invention. Various combinations andselections of various disclosed elements (including the elements in theclaims, example embodiments, drawings, etc.) are possible within thescope of the disclosure of the present invention. Namely, the presentinvention of course includes various variations and modifications thatcould be made by those skilled in the art according to the overalldisclosure including the claims and the technical concept.

The above example embodiments can be described but not limited to as thefollowing notes as examples.

(Supplementary Note 1)

A communication apparatus, comprising:

a first unit for allocating traffic to a dedicated apparatus thatperforms a predetermined network function or a predetermined virtualnetwork function corresponding to the predetermined network function ofthe dedicated apparatus, according to a service level set incorrespondence with information relating to the traffic; and

a second unit for forwarding the traffic to the dedicated apparatus orthe predetermined virtual network function, based on a result of theallocation.

(Supplementary Note 2)

The communication apparatus according to supplementary note 1, whereinthe communication apparatus allocates the traffic, out of virtualmachines which realize the predetermined virtual network function, to afirst virtual machine included in a first virtual network or a secondvirtual machine included in a second virtual network, according to anattribute of the traffic.

(Supplementary Note 3)

The communication apparatus according to supplementary note 1 or 2,wherein the information relating to the traffic includes

information on a carrier, extracted in correspondence with the traffic,a user thereof subscribing to the carrier.

(Supplementary Note 4)

The communication apparatus according to supplementary note 1 or 2,wherein the information relating to the traffic includes

information on contents extracted in correspondence with the trafficthat carries the contents.

(Supplementary Note 5)

The communication apparatus according to supplementary note 1 or 2,wherein the information relating to the traffic includes

information on contents extracted in correspondence with the trafficthat carries the contents.

(Supplementary Note 6)

The communication apparatus according to supplementary note 1 or 2,wherein the information relating to the traffic includes

information on an application of a transmission source of the contents,extracted in correspondence with the traffic.

(Supplementary Note 7)

The communication apparatus according to any one of supplementary notes1 to 6, wherein when allocating the traffic to the virtual networkfunction according to the service level, the first unit selects a serverapparatus including the virtual network function.

(Supplementary Note 8)

The communication apparatus according to any one of supplementary notes1 to 6, wherein the first unit performs the allocation of traffic to thevirtual network function according to the service level set on a pervirtual machine basis, the virtual machine being implemented on a serverapparatus, with the virtual network function running on the virtualmachine.

(Supplementary Note 9)

The communication apparatus according to supplementary note 7, whereinwhen allocating the traffic to the virtual network function according tothe service level, the first unit selects a server apparatus having aprocessing performance corresponding to the service level and includingthe virtual network function, out of a plurality of the serverapparatuses with different processing performances, and allocates thetraffic to a virtual machine that realizes the virtual network functionon the selected server apparatus.

(Supplementary Note 10)

The communication apparatus according to supplementary note 7, theserver apparatus includes

a plurality of the virtual network functions with different processingperformances, arranged on a plurality of the virtual machines, wherein,when allocating the traffic to the virtual network function according tothe service level,

the first unit selects one out of a plurality of the virtual networkfunctions according to the service level, and allocates the traffic to avirtual machine that realizes the selected virtual network function.

(Supplementary Note 11)

The communication apparatus according to supplementary note 7, wherein aplurality of the server apparatuses including the virtual networkfunctions with different functions are provided, each individual serverapparatus including a plurality of the virtual network functions withthe same function and different processing performances,

wherein when allocating the traffic to the virtual network functionaccording to the service level,

the first unit selects a server apparatus having a relevant virtualnetwork function out of a plurality of the server apparatuses, and

selects a virtual network function according to the service level, fromthe plurality of virtual network functions with different processingperformances, on the selected server apparatus to allocate the trafficto a virtual machine that realizes the selected virtual networkfunction.

(Supplementary Note 12)

A communication system, including:

a server apparatus on which a virtual machine that realizes a virtualnetwork function is implemented; and

the communication apparatus according to any one of supplementary notes1 to 11.

(Supplementary Note 13)

An allocation apparatus, including:

a first unit for allocating traffic to a dedicated apparatus thatperforms a predetermined network function or a predetermined virtualnetwork function corresponding to the predetermined network function ofthe dedicated apparatus, according to a service level set incorrespondence with information relating to the traffic; and

a second unit for forwarding the traffic to the dedicated apparatus orthe predetermined virtual network function, based on a result of theallocation.

(Supplementary Note 14)

The allocation apparatus according to supplementary note 13, wherein theallocation apparatus allocates the traffic, out of virtual machineswhich realize the predetermined virtual network function, to a firstvirtual machine included in a first virtual network or a second virtualmachine included in a second virtual network, according to an attributeof the traffic.

(Supplementary Note 15)

The allocation apparatus according to supplementary note 13 or 14,wherein the information relating to the traffic includes

information on a carrier, extracted in correspondence with the traffic,a user thereof subscribing to the carrier.

(Supplementary Note 16)

The allocation apparatus according to supplementary note 13 or 14,wherein the information relating to the traffic includes

information extracted in correspondence with the traffic and beingunique to the user.

(Supplementary Note 17)

The allocation apparatus according to supplementary note 13 or 14,wherein the information relating to the traffic includes informationabout a content which is extracted in correspondence with the trafficand which the traffic carries.

(Supplementary Note 18)

The allocation apparatus according to supplementary note 13 or 14,wherein the information relating to the traffic includes

information on an application of a transmission source of the contents,extracted in correspondence with the traffic.

(Supplementary Note 19)

The allocation apparatus according to any one of supplementary notes 13to 18, wherein when allocating the traffic to the virtual networkfunction according to the service level, the first unit selects a serverapparatus including the virtual network function.

(Supplementary Note 20)

The allocation apparatus according to any one of supplementary notes 13to 18, wherein the first unit performs the allocation of traffic to thevirtual network function according to the service level set on a pervirtual machine basis, the virtual machine being implemented on a serverapparatus, with the virtual network function running on the virtualmachine.

(Supplementary Note 21)

The allocation apparatus according to supplementary note 19, whereinwhen allocating the traffic to the virtual network function according tothe service level, the first unit selects a server apparatus having aprocessing performance corresponding to the service level and includingthe virtual network function, out of a plurality of the serverapparatuses with different processing performances, and allocates thetraffic to a virtual machine that realizes the virtual network functionon the selected server apparatus.

(Supplementary Note 22)

The allocation apparatus according to supplementary note 19, wherein theserver apparatus includes

a plurality of the virtual network functions with different processingperformances, arranged on a plurality of the virtual machines, wherein,when allocating the traffic to the virtual network function according tothe service level,

the first unit selects one out of a plurality of the virtual networkfunctions according to the service level, and allocates the traffic to aselected virtual network function.

(Supplementary Note 23)

The allocation apparatus according to supplementary note 19, wherein aplurality of the server apparatuses including the virtual networkfunctions with different functions are provided, each individual serverapparatus including a plurality of the virtual network functions withthe same function and different processing performances,

wherein when allocating the traffic to the virtual network functionaccording to the service level,

the first unit selects a server apparatus having a relevant virtualnetwork function out of a plurality of the server apparatuses, and

selects a virtual network function according to the service level, fromthe plurality of virtual network functions with different processingperformances, on the selected server apparatus, to allocate the trafficto a virtual machine that realizes the selected virtual networkfunction.

(Supplementary Note 24)

A communication method comprising:

allocating traffic to a dedicated apparatus that performs apredetermined network function or a predetermined virtual networkfunction corresponding to the predetermined network function of thededicated apparatus, according to a service level set in correspondencewith information relating to the traffic; and

forwarding the traffic to the dedicated apparatus or the predeterminedvirtual network function, based on a result of the allocation.

(Supplementary Note 25)

The communication method according to supplementary note 24, comprising

allocating the traffic, out of virtual machines which realize thepredetermined virtual network function, to a first virtual machineincluded in a first virtual network or a second virtual machine includedin a second virtual network, according to an attribute of the traffic.

(Supplementary Note 26)

The communication method according to supplementary note 24 or 25,wherein the information relating to the traffic includes

information on a carrier, extracted in correspondence with the traffic,a user thereof subscribing to the carrier.

(Supplementary Note 27)

The communication method according to supplementary note 24 or 25,wherein the information relating to the traffic includes

information extracted in correspondence with the traffic and beingunique to the user.

(Supplementary Note 28)

The communication method according to supplementary note 24 or 25,wherein the information relating to the traffic includes

information on contents extracted in correspondence with the trafficthat carries the contents.

(Supplementary Note 29)

The communication method according to supplementary note 24 or 25,wherein the information relating to the traffic includes

information on an application of a transmission source of the contents,extracted in correspondence with the traffic.

(Supplementary Note 30)

The communication method according to any one of supplementary notes 24to 29, comprising

when allocating the traffic to the virtual network function according tothe service level, selecting a server apparatus including the virtualnetwork function.

(Supplementary Note 31)

The communication method according to any one of supplementary notes 24to 29, wherein the allocation of traffic to a virtual network functionaccording to a service level is performed per virtual machine which hasbeen implemented on a server apparatus and on which a virtual networkfunction runs.

(Supplementary Note 32)

The communication method according to supplementary note 30, comprising

selecting a server apparatus including the virtual network functioncorresponding to the service level, out of the plurality of serverapparatuses with different processing performances to allocate thetraffic to a virtual machine that realizes the virtual network functionon the selected server apparatus.

(Supplementary Note 33)

The communication method according to supplementary note 30, wherein theserver apparatus includes a plurality of the virtual network functionswith different processing performances, arranged on a plurality of thevirtual machines, the method comprising

selecting one out of the plurality of virtual network functionsaccording to the service level to allocate the traffic to the selectedvirtual network function.

(Supplementary Note 34)

The communication method according to supplementary note 30, wherein aplurality of the server apparatuses including the virtual networkfunctions with different functions are provided, each individual serverapparatus including a plurality of the virtual network functions withthe same function and different processing performances, the methodcomprising:

selecting the server apparatus having a relevant virtual networkfunction out of the plurality of server apparatuses; and

selecting a virtual network function according to the service level,from the plurality of virtual network functions with differentprocessing performances, on the selected server apparatus to allocatethe traffic to the selected virtual network function.

(Supplementary Note 35)

A non-transitory computer-readable recording medium storing therein aprogram causing a computer to execute:

a first processing for allocating traffic to a dedicated apparatus thatperforms a predetermined network function or a predetermined virtualnetwork function corresponding to the predetermined network function ofthe dedicated apparatus, according to a service level set incorrespondence with information relating to the traffic; and

a second processing for forwarding the traffic to the dedicatedapparatus or the predetermined virtual network function, based on aresult of the allocation.

(Supplementary Note 36)

The non-transitory computer-readable recording medium according tosupplementary note 35, the medium storing a program causing the computerto perform processing comprising

allocating the traffic, out of virtual machines which realize thepredetermined virtual network function, to a first virtual machineincluded in a first virtual network or a second virtual machine includedin a second virtual network, according to an attribute of the traffic.

(Supplementary Note 37)

The non-transitory computer-readable recording medium according tosupplementary note 35 or 36, wherein the information relating to thetraffic includes

information on a carrier, extracted in correspondence with the traffic,a user thereof subscribing to the carrier.

(Supplementary Note 38)

The non-transitory computer-readable recording medium according tosupplementary note 35 or 37, wherein the information relating to thetraffic includes

information extracted in correspondence with the traffic and beingunique to the user.

(Supplementary Note 39)

The non-transitory computer-readable recording medium according tosupplementary note 35 or 36, wherein the information relating to thetraffic includes

information on contents extracted in correspondence with the trafficthat carries the contents.

(Supplementary Note 40)

The non-transitory computer-readable recording medium according tosupplementary note 35 or 36, wherein the information relating to thetraffic includes

information on an application of a transmission source of the contents,extracted in correspondence with the traffic.

(Supplementary Note 41)

The non-transitory computer-readable recording medium according to anyone of supplementary notes 35 to 40, wherein, when the traffic isallocated to the virtual network function according to the servicelevel, the first processing select a server apparatus including thevirtual network function.

(Supplementary Note 42)

The non-transitory computer-readable recording medium according to anyone of supplementary notes 35 to 40, wherein, the first processingperforms the allocation of traffic to a virtual network functionaccording to a service level on a per virtual machine basis, the virtualmachine, on which the virtual network function runs, being implementedon a server apparatus.

(Supplementary Note 43)

The non-transitory computer-readable recording medium according tosupplementary note 42, wherein when allocating the traffic to thevirtual network function according to the service level, the firstprocessing selects a server apparatus having a processing performancecorresponding to the service level and including the virtual networkfunction, out of a plurality of the server apparatuses with differentprocessing performances, and allocates the traffic to a virtual machinethat realizes the virtual network function on the selected serverapparatus.

(Supplementary Note 44)

The non-transitory computer-readable recording medium according tosupplementary note 42, wherein the server apparatus includes a pluralityof virtual network functions with different processing performances on aplurality of virtual machines, and wherein when allocating traffic to avirtual machine that realizes the virtual network function according tothe service level,

the first processing selects one of the plurality of virtual networkfunctions according to the service level to allocate the traffic to avirtual machine that realizes the selected virtual network function.

(Supplementary Note 45)

The non-transitory computer-readable recording medium according tosupplementary note 42, wherein a plurality of the server apparatusesincluding the virtual network functions with different functions areprovided, each individual server apparatus including a plurality of thevirtual network functions with the same function and differentprocessing performances,

wherein when allocating the traffic to the virtual network functionaccording to the service level,

the first processing selects a server apparatus having a relevantvirtual network function out of a plurality of the server apparatuses,and

selects a virtual network function according to the service level, fromthe plurality of virtual network functions with different processingperformances, on the selected server apparatus to allocate the trafficto a virtual machine that realizes the selected virtual networkfunction.

What is claimed is:
 1. A communication apparatus comprising: a memoryconfigured to store instructions; and a processor configured to executethe instructions to: identify a user of traffic received; allocate thetraffic to a physical node or a virtual node including a networkfunction of the physical node, according to a service contract of theuser; and forward the traffic to one of the physical node and thevirtual node, based on a result of the allocation, wherein the processorallocates the traffic to the virtual node according to the servicecontract of the user and a performance level of the virtual node in acase when the processor allocates traffic to the virtual node, theperformance level of the virtual node including at least one of a numberof virtual CPUs, a virtual memory capacity, a number of virtual NICs, abandwidth thereof and a virtual storage capacity allocated to thevirtual node.
 2. The communication apparatus according to claim 1,wherein the processor allocates the traffic to the virtual node selectedfrom a high function type virtual node, a medium function type virtualnode and a low function type virtual node, according to the servicecontract of the user.
 3. The communication apparatus according to claim1, wherein the processor allocates the traffic to the physical node orthe virtual node, according to a service level of the service contractof the user.
 4. The communication apparatus according to claim 3,wherein the processor allocates the traffic to the physical node in casewhen the service level of the service contract of the user is higherthan a predetermined level and to the virtual node in case when theservice level of the service contract of the user is lower than or equalto the predetermined level.
 5. The communication apparatus according toclaim 4, wherein the service level is set based on communication speed,Quality of Service or contract price.
 6. A communication methodcomprising: identifying a user of traffic received; allocating thetraffic to a physical node or a virtual node including a networkfunction of the physical node, according to a service contract of theuser; forwarding the traffic to one of the physical node and the virtualnode, based on a result of the allocation; and allocating the traffic tothe virtual node according to the service contract of the user and aperformance level of the virtual node in a case when allocating thetraffic to the virtual node, the performance level of the virtual nodeincluding at least one of a number of virtual CPUs, a virtual memorycapacity, a number of virtual NICs, a bandwidth thereof and a virtualstorage capacity allocated to the virtual node.
 7. The communicationmethod according to claim 6, comprising allocating the traffic to thevirtual node selected from a high function type virtual node, a mediumfunction type virtual node and a low function type virtual node,according to the service contract of the user.
 8. The communicationmethod according to claim 6, comprising allocating the traffic to thephysical node or the virtual node, according to a service level of theservice contract of the user.
 9. The communication method according toclaim 8, comprising allocating the traffic to the physical node in casewhen the service level of the service contract of the user is higherthan a predetermined level and to the virtual node in case when theservice level of the service contract of the user is lower than or equalto the predetermined level.
 10. The communication method according toclaim 9, wherein the service level is set based on communication speed,Quality of Service or contract price.
 11. A non-transitory computerreadable medium storing thereon a program causing a computer to executeprocessing comprising: identifying a user of traffic received;allocating the traffic to a physical node or a virtual node including anetwork function of the physical node, according to a service contractof the user; forwarding the traffic to one of the physical node and thevirtual node, based on a result of the allocation; and allocating thetraffic to the virtual node according to the service contract of theuser and a performance level of the virtual node in a case whenallocating the traffic to the virtual node, the performance level of thevirtual node including at least one of a number of virtual CPUs, avirtual memory capacity, a number of virtual NICs, a bandwidth thereofand a virtual storage capacity allocated to the virtual node.
 12. Thenon-transitory computer readable medium according to claim 11,comprising allocating the traffic to the virtual node selected from ahigh function type virtual node, a medium function type virtual node anda low function type virtual node, according to the service contract ofthe user.
 13. The non-transitory computer readable medium according toclaim 11, comprising allocating the traffic to the physical node or thevirtual node, according to a service level of the service contract ofthe user.
 14. The non-transitory computer readable medium according toclaim 13, comprising allocating the traffic to the physical node in casewhen the service level of the service contract of the user is higherthan a predetermined level and to the virtual node in case when theservice level of the service contract of the user is lower than or equalto the predetermined level.
 15. The non-transitory computer readablemedium according to claim 14, wherein the service level is set based oncommunication speed, Quality of Service or contract price.